NTISthis.com

Evidence Guide: ICTPRG416 - Manage a software component re-use library

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG416 - Manage a software component re-use library

What evidence can you provide to prove your understanding of each of the following citeria?

Specify the components for re-use library

  1. Determine component suitability for reuse by checking its quality, and uses
  2. Review the size and complexity of re-use components for generalisation, and remove project-specific refinements
  3. Evaluate the components, including patterns, clusters and frameworks, and break them down into smaller components for greater flexibility or use
  4. Review the components for duplication, and remove the duplicates
Determine component suitability for reuse by checking its quality, and uses

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the size and complexity of re-use components for generalisation, and remove project-specific refinements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate the components, including patterns, clusters and frameworks, and break them down into smaller components for greater flexibility or use

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the components for duplication, and remove the duplicates

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the re-use library

  1. Document the components internally and externally, to ensure efficient retrieval
  2. Document public constants, data structures, component interfaces and limitations
  3. Document the possible relationships between data structures or objects
  4. Provide an example code, demonstrating the use of components within the documentation
  5. Document the development environment configuration
  6. Provide simple test programs to prove the functionality of the library
Document the components internally and externally, to ensure efficient retrieval

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document public constants, data structures, component interfaces and limitations

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the possible relationships between data structures or objects

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Provide an example code, demonstrating the use of components within the documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the development environment configuration

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Provide simple test programs to prove the functionality of the library

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Set up the library structure

  1. Classify data structures or objects in a consistent and logical manner
  2. Ensure that the library has a logical structure so that the user is aware of the library contents, and can understand the logic of how the functionality may be used by another developer
  3. Develop the structure in such a manner that it avoids redundancy within the library
  4. Configure the development environment to automate the build of re-use components, and the library
  5. Take action to ensure that interfaces to the library components are consistent and abstracted
  6. Add, update, and remove re-use components, as development is undertaken
Classify data structures or objects in a consistent and logical manner

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure that the library has a logical structure so that the user is aware of the library contents, and can understand the logic of how the functionality may be used by another developer

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop the structure in such a manner that it avoids redundancy within the library

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Configure the development environment to automate the build of re-use components, and the library

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure that interfaces to the library components are consistent and abstracted

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Add, update, and remove re-use components, as development is undertaken

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Specify the components for re-use library

1.1 Determine component suitability for reuse by checking its quality, and uses

1.2 Review the size and complexity of re-use components for generalisation, and remove project-specific refinements

1.3 Evaluate the components, including patterns, clusters and frameworks, and break them down into smaller components for greater flexibility or use

1.4 Review the components for duplication, and remove the duplicates

2. Document the re-use library

2.1 Document the components internally and externally, to ensure efficient retrieval

2.2 Document public constants, data structures, component interfaces and limitations

2.3 Document the possible relationships between data structures or objects

2.4 Provide an example code, demonstrating the use of components within the documentation

2.5 Document the development environment configuration

2.6 Provide simple test programs to prove the functionality of the library

3. Set up the library structure

3.1 Classify data structures or objects in a consistent and logical manner

3.2 Ensure that the library has a logical structure so that the user is aware of the library contents, and can understand the logic of how the functionality may be used by another developer

3.3 Develop the structure in such a manner that it avoids redundancy within the library

3.4 Configure the development environment to automate the build of re-use components, and the library

3.5 Take action to ensure that interfaces to the library components are consistent and abstracted

3.6 Add, update, and remove re-use components, as development is undertaken

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Specify the components for re-use library

1.1 Determine component suitability for reuse by checking its quality, and uses

1.2 Review the size and complexity of re-use components for generalisation, and remove project-specific refinements

1.3 Evaluate the components, including patterns, clusters and frameworks, and break them down into smaller components for greater flexibility or use

1.4 Review the components for duplication, and remove the duplicates

2. Document the re-use library

2.1 Document the components internally and externally, to ensure efficient retrieval

2.2 Document public constants, data structures, component interfaces and limitations

2.3 Document the possible relationships between data structures or objects

2.4 Provide an example code, demonstrating the use of components within the documentation

2.5 Document the development environment configuration

2.6 Provide simple test programs to prove the functionality of the library

3. Set up the library structure

3.1 Classify data structures or objects in a consistent and logical manner

3.2 Ensure that the library has a logical structure so that the user is aware of the library contents, and can understand the logic of how the functionality may be used by another developer

3.3 Develop the structure in such a manner that it avoids redundancy within the library

3.4 Configure the development environment to automate the build of re-use components, and the library

3.5 Take action to ensure that interfaces to the library components are consistent and abstracted

3.6 Add, update, and remove re-use components, as development is undertaken

Evidence of the ability to:

manage a software component re-use library

specify the re-use library components

document the re-use library components

ensure logical structuring and interface facilitate retrieval and use.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain abstraction of code module interfaces

describe the features of component libraries

explain the design paradigms

describe patterns, frameworks and idioms

describe the re-use components, and metrics

describe the content and structure of re-use libraries.